Select one the following options to set an execution priority for the linked Case model:

• Same as Main Process - Priority is same as defined in the main process.
• Same as Sub Case - Priority is same as defined in the linked Case model.
• Other - To specify the execution priority that is different to the main process and the linked Case model, select one of the following:
  
  • Static - You can select any one of the priority levels: Highest, High, Normal, Low, and Lowest.
  • Read from message - If you want to dynamically set the execution priority.

    Note: If the Read from Message is selected and an invalid value is provided, then the priority of the parent case will be considered; value will be considered invalid, if it is either empty, non-numeric, or contains a value less than 1 or greater than 5.

The Execute Condition can be of types - None, Static Value, or Read From Message. Select the Static Value option to specify the actual condition for execution.Select the Read From Message option to read the condition from the XPath of the message. You can build a condition by clicking the XPath editor icon ( ) appearing at the end of this field.

Note:

• Ensure that the Read From Message condition which is taken from the Message Map does not start with a slash.
• If a message contains an XPath expression, then the XPath need not be in single quotes. For example, if the message is /mycondition and it contains an expression as follows: GetEmployeeOutput/GetEmployeeResponse/tuple/old/Employees/City = "London".
• If the specified execute condition is satisfied, the activity is executed, otherwise it is skipped.
  In a subprocess construct, the Execute Condition option can be used instead of the Decision construct. Thus, you do not need to explicitly model a decision construct when only one path from the Decision construct leads to an activity.You can view the decision icon on the left bottom corner of the construct indicating that the activity includes a condition for execution.

Refers to the level of monitoring that you want to set on the Independent subprocess activity.

• Activity status: Records activity status, timestamp, and user information.
• Activity status, input and output messages: Records the input and output messages of the activity along with its status.
• Store complete activity information when activity aborts: Records activity status and input and output messages information only when the process aborts. If the activity is successfully completed, none of the monitoring information is recorded.
  
  Note: Monitoring options at activity level are dependent upon the options defined at the process level in the Default Activity Monitoring tab. You can override the monitoring activity and store the relevant recovery point settings to each individual activity level, by clicking the Apply Default Settings button.